Method for Updating and Managing Synchronization Identifier by using Release Messages or Status Request and Response

ABSTRACT

A method for communicating additional network information using a synchronization identifier is presented. A synchronization identifier is defined. The synchronization identifier is used for the purpose of synchronizing communication between a Mobile Station (MS) and a network. In addition, the synchronization identifier is used to define additional functionality in the wireless network. As such, the synchronization identifier may be used to communicate information about wireless services and/or wireless components between the MS and the network.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority from application Ser. No. 60/______entitled “METHOD AND APPARATUS FOR UPDATING AND MANAGING SYNCHRONIZATIONIDENTIFIER BY USING RELEASE MESSAGES OR STATUS REQUEST AND RESPONSE”filed on Jul. 8, 2003, the contents of which are incorporated herein byreference.

FIELD OF THE INVENTION

This invention relates to communication networks. Specifically, thepresent invention relates to wireless communication networks.

DESCRIPTION OF THE PRIOR ART

In a conventional wireless network, a Mobile Station (MS) may be used byan end user to access network services. The MS includes interfaceequipment used to terminate a wireless signal at the end-user side of acommunication link. Examples of an MS include a cellular telephone, awireless laptop, etc.

The MS communicates with a Base Station System (BS). The BS performsradio-related functions. The BS includes Base Transceiver Stations(BTSs) and a Base Station Controller (BSC). The BTS provides aninterface to the MS. In one embodiment, the BTS includes radioequipment, such as the transceivers and antennas, needed to service eachcell in a wireless network. Several BTSs are typically controlled by aBSC. The BSC provides control functions and physical links between aMessage Switching Center (MSC) and the BTS. The MSC provides aninterface to network functionality, such as an internal network, virtualprivate networks, public service telephone networks, etc.

During operation, configuration information is communicated between theMS and BS to facilitate communications. The configuration information issynchronized between the MS and the BS for proper operation of thesystem. One specific type of synchronization information is Sync_IDinformation (i.e., Sync_ID) as defined by TIA/EIA IS-2000.5-C, SignalingStandards for cdma2000 Spread Spectrum Systems—Release C, May 2002. TheSync_ID information is communicated between the MS and the BS instandardized messages to ensure that configuration information iscurrent and updated between the MS and the BS.

With the tremendous increase in wireless technology, bandwidth is at apremium in most wireless systems. Therefore, a number of techniques havebeen developed to increase bandwidth. However, many of these techniquesfocus on developing hardware and software that increases speed andprocessing power. However, the development cost and additionalcomplexity associated with developing hardware and software is oftenprohibitive.

Thus, there is a need for a method and apparatus for increasingperformance and functionality of wireless networks within the context ofthe current signaling and message structure of standardized protocols.There is a need for a method and apparatus that utilizes the Sync_IDinformation to increase performance and functionality of wirelessnetworks within the framework of various wireless standard.

SUMMARY OF THE INVENTION

The present invention is directed to a method and apparatus forincreasing performance and functionality of wireless networks thatutilize standardized messages. In one embodiment, additional networkfunctions are implemented in a wireless network by utilizingsynchronization information, such as the Sync_ID information (i.e.,Sync_ID) defined in TIA/EIA IS-2000.5-C, Signaling Standards forcdma2000 Spread Spectrum Systems—Release C, May 2002.

In one embodiment, additional meaning is associated with synchronizationinformation, such as Sync_IDs, by mapping and/or correlating thesynchronization information to additional information. Standardizedmessages are then used to communicate the synchronization informationbetween the MS and the BS. For example, additional meaning is attributedto the synchronization information. As such, the synchronizationinformation may be used to facilitate the synchronization of the MS andthe BS and the same synchronization information may also be used tocommunicate additional information between the MS and the BS to provideadditional functionality in the wireless system.

Additional network functions may be implemented using synchronizationinformation. In one embodiment, the synchronization information may beused to define and/or communicate information about network servicesand/or network components. As a result, in addition to performing theprimary function of synchronizing configuration information between theMS and the network, the synchronization information may also be used tocommunicate additional information, such as information about networkservices and/or network components. The additional information is theninterpreted and used to implement additional network functions. As aresult, the synchronization information is used to add functionality tothe wireless system.

In one embodiment, the synchronization information is mapped to networkservices. For example, specific synchronization information may be usedto represent a web browsing service. As such, when the synchronizationinformation is communicated between the MS and the BS, information aboutthe web browsing service is communicated between the MS and the BS.

In another embodiment, the synchronization information may be mapped tonetwork components. As such, when the synchronization information iscommunicated between the MS and the BS, information about the networkcomponents is communicated between the MS and the BS. For example,information on whether a component exists in the network may becommunicated using the synchronization information; informationidentifying a specific gateway that should be used to provide a betterquality of service may be communicated using the synchronizationinformation, etc.

Using the synchronization information to communicate information aboutnetwork services and/or network components enables the implementation ofadditional network functions. As such, in accordance with the teachingsof the present invention, the synchronization information is used toprovide additional functionality in the wireless network. It should beappreciated that although specific network functions are defined anddescribed, a variety of additional network functions may be defined anddescribed using the synchronization information.

In accordance with the teachings of the present invention, a method ofoperating comprises the steps of receiving synchronization informationusing network messaging, the synchronization information capable of usefor synchronization; and then implementing a network function other thansynchronization by interpreting the synchronization information.

A method for managing a synchronization identifier, comprises embeddinga first synchronization identifier in a release order; transmitting therelease order; and causing update of a second synchronization identifierusing the first synchronization identifier received in the releaseorder.

A method for managing a synchronization identifier, comprises formattinga status request at a base station for checking a mobile stationsynchronization identifier; transmitting the status request to a mobilestation, the status request causing the mobile station to transmit astatus response that includes the mobile station synchronizationidentifier; receiving the status response; and if the mobile stationsynchronization identifier does not match the base stationsynchronization identifier, transmitting an update request to the mobilestation that includes the base station synchronization identifier.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 displays a network implementing the teachings of the presentinvention.

FIG. 2 displays a computer architecture implementing the teachings ofthe present invention.

FIG. 3 displays a data diagram displaying the mapping between thesynchronization information and different of network functions.

FIG. 4A displays a data diagram displaying the mapping between a packetincluding synchronization information and specific network functions.

FIG. 4B displays a data diagram displaying the mapping between a packetincluding a field including synchronization information and variousnetwork functions.

FIG. 5 displays a message flow diagram in which a BS updates Sync_IDwith a Release Order Message.

FIG. 6 displays a message flow diagram in which a BS updates a Sync_IDwith a Release Order on Common Channel.

FIG. 7A displays a message flow diagram in which the MS performs aquery.

FIG. 7B displays a message flow diagram in which the BS performs aquery.

DESCRIPTION OF THE INVENTION

While the present invention is described herein with reference toillustrative embodiments for particular applications, it should beunderstood that the invention is not limited thereto. Those havingordinary skill in the art and access to the teachings provided hereinwill recognize additional modifications, applications, and embodimentswithin the scope thereof and additional fields in which the presentinvention would be of significant utility.

It should be appreciated that although the present invention will bedescribed with respect to TIA/EIA IS-2000.5-C, Signaling Standards forcdma2000 Spread Spectrum Systems—Release C, May 2002, it is fullyanticipated that this standard will evolve and that the evolvedstandards are within the scope of the present invention. Further, isshould also be appreciated that the underlying teachings of the presentinvention are applicable to various other standards associated with theevolved standards.

A variety of terms defined in TIA/EIA IS-2000.5-C, Signaling Standardsfor cdma2000 Spread Spectrum Systems—Release C, May 2002 will be used inthe present invention. BS is used to represent a base station. MS isused to represent a mobile station. Various types of configurationinformation are defined. For example, NNSCR is a non-negotiable serviceconfiguration information record. The NNSCR contains non-negotiableservice configuration parameters of a call. The ERM is an ExtendedRelease Message. One type of synchronization information is the ServiceConfiguration Information Record or SCR. The SCR contains the serviceconfiguration parameters of a call. Synchronization information includesthe Sync_ID, which is a Service Configuration SynchronizationIdentifier. The Sync_ID is a variable length identifier corresponding tothe SCR and NNSCR that may be stored by the base station and/or themobile station. In one embodiment, the Sync_ID value is used by the basestation to determine whether SCR and NNSCR may be omitted during thecall set up.

In accordance with the teachings of the present invention,synchronization information is communicated using standardized networkmessaging. The synchronization information is then used (1) for thepurpose of synchronizing components in the network and (2) for addingadditional network functions (i.e., additional network functionality) tothe network. In one embodiment of the present invention, thestandardized network messaging includes standardized messages defined bycommunications protocols. For example, protocols defined by the 3^(rd)generation partnership project (i.e., 3GPP2), such as the 3G wirelessprotocol, protocols defined by the Internet Engineering Task Force(i.e., IETF), such as various internet protocols, etc. It should beappreciated that although two specific standards groups and family ofprotocols are discussed, the present invention applies to a variety ofstandards-based groups and communications protocols and messagingdefined by the standards-based groups.

In one embodiment, the standardized messaging defined in TIA/EIAIS-2000.5-C, Signaling Standards for cdma2000 Spread SpectrumSystems—Release C, May 2002 is used to implement the present invention.For example, in one embodiment, Release Order Messages as defined inTIA/EIA IS-2000.5-C, Signaling Standards for cdma2000 Spread SpectrumSystems—Release C, May 2002 are used to communicate the synchronizationinformation. In another embodiment, a Universal Handoff Messaging asdefined in TIA/EIA IS-2000.5-C, Signaling Standards for cdma2000 SpreadSpectrum Systems—Release C, May 2002 is used to communicate thesynchronization information.

The synchronization information is then used to add additional functions(i.e., functionality) to the network. In one embodiment, additionalfunctionality includes a scenario in which the synchronizationinformation is used to implement another function in addition tosynchronization. For example, the synchronization information may beused to implement an additional service in the wireless network, such asvideo services, wireless services, Internet services, etc. Further, thesynchronization information may be used to identify a component ornetwork in the wireless network, such as a gateway, router, bridge, etc.For example, identifying various devices for communication may enablethe network to implement functions, such as quality of service or loadbalancing, by routing traffic through various components in the wirelessnetwork.

In one embodiment, the additional function is implemented by mapping orcorrelating the synchronization information with values, numbers,symbols, etc. that have a predefined meaning and/or values, numbers,symbols that may be used to implement a predefined function. Forexample, in one embodiment, databases may be deployed in an MS andplaced in association (i.e., in communication) with a BS. Whensynchronization information is communicated between the MS and the BSthe synchronization information may be used to synchronize the twodevices.

In addition, the synchronization information may be used as an index tomap or correlate a value, number, symbol, etc. found in one or both ofthe databases. The value may be used to represent a service and/orcomponent in the network. For example, the value may represent a videoservice or a router in the network. In the case where the valuerepresents a video service, communicating the synchronizationinformation between the MS and the BS provides information about thevideo service and, as such, facilitates the implementation of the videoservice in the network. In this scenario, the synchronizationinformation is used to implement an additional network function or toadd additional functionality in the network. In this example, theadditional network function or functionality is the video service.

In the case where the value represents a device, such as a router in thenetwork, communicating the synchronization information between the MSand the BS provides information that identifies the router and, as such,facilitates the use of the router in the network. As such, thesynchronization information has been used to implement an additionalfunction in the network or to add additional functionality in thenetwork. The additional function or functionality is the identificationof a specific device, such as the router that should be used forcommunication. As a result, functionality, such as load balancing andquality of service, may be realized by identifying which device to useto communicate traffic at a specific time.

FIG. 1 displays a network implementing the teachings of the presentinvention. A mobile station (MS) 100 is in communication with a basestation (BS) 104. The MS 100 and the BS 104 synchronize information,such as a Sync_ID. The BS 104 may communicate with a network 108.

In one embodiment, the MS 100 includes or is in communication with adatabase (ms) 102. The database (ms) 102 may store synchronizeinformation. For example, several Sync_IDs may be simultaneously storedin the database (ms) 102. The BS 104 also communicates with a database(bs) 106. The database (bs) 106 may also store various types ofsynchronization information, such as one or several Sync_IDs. It shouldbe appreciated that although the database (bs) 106 is showncommunicating with the BS 104, the database (bs) 106 may communicateacross a network, such as network 108 with the BS 104.

In one embodiment, each database, database (ms) 102 and the database(bs) 106 may be used to implement additional network functions in thewireless network by mapping or correlating the synchronize informationto a number, value, symbol, code, etc. that represents a componentand/or service in the wireless network. For example, the database (ms)102 and the database (bs) 106 may each be implemented as a relationaldatabase and perform a mapping or correlation between the synchronizeinformation and a value representing a wireless service, such as anInternet service, wireless video, wireless audio, etc. As such, inaddition to synchronizing configuration information between the MS 100and the network 108 (i.e., BS 104), the synchronize information may beused to provide additional functionality to the wireless network bycommunicating information about network services.

In an alternative embodiment, the synchronization information may beused to implement a number, symbol, etc. that performs a mapping and/orcorrelation between the synchronization information and a component inthe network, such as the MSC, a specific router, a specific end device.As such, the synchronization information may be used to implement,initiate, or communicate information about a specific device in thenetwork. The device may then be used to distribute traffic. For example,load balancing may be achieved using the synchronization information. Assuch, in addition to synchronizing configuration information between theMS 100 and the network 108 (i.e., base station 104), the synchronizationinformation is used to provide additional functionality in the wirelessnetwork by communicating information about network components.

During operation, synchronization information is communicated betweenthe MS 100 and the BS 104. In one embodiment, the synchronizationinformation may be used to represent configuration information, such asSCR and NNSCR. However, various types of configuration information maybe represented and still remain within the scope of the presentinvention.

In accordance with the teachings of the present invention, standardizedmessages as defined in TIA/EIA IS-2000.5-C, Signaling Standards forcdma2000 Spread Spectrum Systems—Release C, May 2002 and associatedspecifications may be used to communicate the synchronizationinformation between MS 100 and BS 104. For example, in one embodiment,Release Order Messages as defined in TIA/EIA IS-2000.5-C, SignalingStandards for cdma2000 Spread Spectrum Systems—Release C, May 2002 andassociated specifications may be used to communicate the synchronizationinformation between MS 100 and BS 104. For example, the releasemessages, such as the Release Order Message, the Extended ReleaseMessage and/or the Extended Release Mini-Message, etc., may beimplemented.

In another embodiment, Handoff Messages as defined in TIA/EIAIS-2000.5-C, Signaling Standards for cdma2000 Spread SpectrumSystems—Release C, May 2002 and associated specifications may be used tocommunicate the synchronization information between MS 100 and BS 104.In one embodiment, Handoff Messages as defined in TIA/EIA IS-2000.5-C,Signaling Standards for cdma2000 Spread Spectrum Systems—Release C, May2002 and associated specifications, such as a Universal HandoffDirection Message, may be implemented.

Once the synchronization information is communicated between the MS 100and the BS 104, the configurations between the MS 100 and the BS 104 maybe synchronized. In addition, in accordance with the teachings of thepresent invention, the synchronization information may be used toprovide additional functionality to the wireless network depicted inFIG. 1. For example, in one embodiment, the synchronization informationmay be used as an index to search database (ms) 102 and/or database (bs)106. The synchronization information may map or correlate with a value,symbol, number, etc. representing a service, component, etc. in anetwork. As such, by communicating the synchronization information andthen storing, searching, mapping, correlating, and/or using thesynchronization information in association with the database (ms) 102and the database (bs) 106, additional network information about networkcomponents and/or services are communicated with the synchronizationinformation. Additional network information may include information usedto implement additional functions in the network, such as informationused to implement additional network services, information used toidentify specific components or networks, information used to launchautomated routines in the MS 100 or BS 104, information used toautomatically configure network 108, etc.

In one embodiment of the present invention, the synchronizationinformation is used to implement fast call setup related features. Forexample, the BS 104 assigns synchronization information representing theconfigurations (i.e., Sync_ID which represents SCR and NNSCR) that areassociated with service option(s) associated with the MS 100 (i.e.,based on end user subscription policy, criteria, etc.). When either side(i.e., BS 104 and/or MS 100) connects a call using these serviceoptions, the BS 104 or the MS 100 can use the synchronizationinformation to identify the stored configurations for the call. Forexample, in one embodiment, packet data service (i.e., web browsing) canuse the synchronization information when the service is connected anddisconnected between an idle state and a traffic state.

In addition to the configuration information, such as the SCR and theNNSCR that the synchronization information is used to represent, inaccordance with the teachings of the present invention, thesynchronization information itself can carry additional usefulinformation and, as such, provide additional functionality in thewireless system. For example, various types of Internet protocolinformation, such as the MS's Internet protocol version 4 (i.e., IPv4)address and/or the Generic Routing Encapsulation (GRE) Key informationfor the packet data service option of the MS, may be communicated usingthe synchronization information. As such, the BS 104 may use thesynchronization information itself during the service optionreconnection to speed up the connection or for other purposes.

In one embodiment, synchronization information includes a base stationsynchronization identifier (BSSI) and a mobile station synchronizationidentifier (MSSI). In one embodiment, the BSSI may be used tocommunicate the current configuration status of the BS 104. The MSSI issynchronization information that is used to convey the currentsynchronization status of the MS 100.

During operation, the BS 104 may communicate the BSSI to the MS 100 andthe MS 100 may communicate the MSSI to the BS 104. For example, usingFIG. 1 BS 104 may communicate the BSSI to the MS 100. The MS 100 maythen optionally store the MSSI in the database (ms) 102. In addition,the MS 100 may communicate the MSSI to the BS 104. The BS 104 may thenoptionally store the BSSI in the database (bs) 106.

In accordance with the teachings of the present invention, the BS 104may embed the BSSI in a standardized communication message. For example,in one embodiment, the BS 104 may embed the BSSI in a Release OrderMessage, such as the Release Order Messages as defined in TIA/EIAIS-2000.5-C, Signaling Standards for cdma2000 Spread SpectrumSystems—Release C, May 2002 and associated specifications. In oneembodiment, the Release Messages include the Release Order Message, theExtended Release Message, and/or the Extended Release Mini-Message.

The BS 104 may then transmit the Release Message to the MS 100. The MS100 receives the Release Message communicated by the BS 104 and is thenable to update the MSSI using the BSSI embedded in the Release Message.In another embodiment, the MS 100 may then transmit the Release Messageto the BS 104. The BS 104 receives the Release Message communicated bythe MS 100. The BS 104 may embed a BSSI in a Release Message. The BS 104may then transmit the Release Message to the MS 100. The MS 100 receivesthe Release Message communicated by the BS 104 and is then able toupdate the MSSI using the BSSI embedded in the Release Message.

It should be appreciated that the foregoing method may be implementedwhile the MS 100 and the BS 104 are operating on the traffic channel orin the idle state. In addition, the BSSI may be used to communicateadditional information used to implement network functions. For example,in one embodiment, the BSSI is used to communicate additional serviceinformation, such as mobile IP information or GRE tunnel information. Inanother embodiment, the BSSI may be used to communicate additionalnetwork component information, such as a specific device to use duringthe communication session. Lastly, it should be appreciated that theRelease Message may include multiple instances of synchronizationinformation, such as multiple BSSIs or multiple MSSIs.

In another embodiment of the present invention, during operation astatus request is formulated at the BS 104. The status request isformulated to check the current MSSI in the MS 100. The status requestis transmitted from the BS 104 to the MS 100. After receiving the statusrequest at the MS 100, a status response is formulated by the MS 100.The status response includes the MSSI associated with the MS 100. Thestatus response is transmitted to the BS 104. The BS 104 then checks todetermine if the MSSI transmitted by the MS 100 matches the current MSSIstored in association with the BS 104. If the MSSI does not match thecurrent BSSI, then an update request including the current MSSI istransmitted from the BS 104 to the MS 100.

FIG. 2 displays a computer architecture implementing the teachings ofthe present invention. The computer 200 of FIG. 2 may implement themobile station (MS) 100, the database (ms) 102, the base station (BS)104, the database (bs) 106, and the network 108 of FIG. 1. A centralprocessing unit (CPU) 202 functions as the brain of the computer 200.Internal memory 204 is shown. The internal memory 204 includesshort-term memory 206 and long-term memory 208. The short-term memory206 may be a Random Access Memory (RAM) or a memory cache used forstaging information. The long-term memory 208 may be a Read Only Memory(ROM) or an alternative form of memory used for storing information.Storage memory 220 may be any memory residing within the computer 200other than internal memory 204. In one embodiment of the presentinvention, storage memory 220 is implemented with a hard drive. Acommunication pathway 210 is used to communicate information withincomputer 200. In addition, the communication pathway 210 may beconnected to interfaces, which communicate information out of thecomputer 200 or receive information into the computer 200.

Input devices, such as tactile input device, joystick, keyboards,microphone, communications connections, or a mouse, are shown as 212.The input devices 212 interface with computer 200 through an inputinterface 214. Output devices, such as a monitor, speakers,communications connections, etc., are shown as 216. The output devices216 communicate with computer 200 through an output interface 218.

FIG. 3 depicts a data diagram displaying a mapping between thesynchronization information and different network functions. Thesynchronization information 300 is mapped to various network functions302 (i.e., functionality). For example, the synchronization informationis mapped to network components 304. In one embodiment, the networkcomponents 304 may include an MSC, routers, base stations, MS, etc. Whenthe synchronization is mapped to a network component as shown at 304,information about a specific network component may be communicatedbetween the BS and the MS during synchronization using thesynchronization information. As such, routing, load balancing, etc. maybe implemented using the synchronization information.

In a second embodiment, network services 306 may be communicated,initiated, and implemented using the synchronization information. Forexample, network services, such as Internet services, web services,maintenance services, audio services, video services, etc., may beimplemented using the synchronization information 300. As such, usingthe synchronization information provides another option forcommunicating information about services between the MS and the network.

FIG. 4A displays a data diagram displaying the mapping between a packetincluding synchronization information and specific network functions. InFIG. 4A, a data packet including a field comprising synchronizationinformation 400 is mapped to a network function(s) 402. In oneembodiment, the field comprising synchronization information 400 ismapped to a specific network function, such as a network service, anetwork component, etc. For example, a one-to-one mapping is performedbetween the synchronization information 400 and specific networkfunction.

FIG. 4B displays a data diagram displaying the mapping between a packetincluding a field including synchronization information and variousnetwork functions. In a second embodiment, a field comprisingsynchronization information 404 is mapped to several network functionsas shown by 406 to 408. For example, one field comprisingsynchronization information 404 may be mapped to a network function(s)406 to 408 where the network function(s) 406 to 408 may representseveral network services or several network components. For example, inone embodiment, the field comprising synchronization information 404 maybe segmented into several fields comprising synchronization informationas shown by 404A or 404B. Each field comprising synchronizationinformation, such as 404A and 404B may be linked to a specific networkservice.

In an alternative embodiment, synchronization information 404 may beused to implement a variety of different network functions. For example,a single instance of synchronization information may be used torepresent multiple components or multiple services. In addition, anypermutation or combination of the foregoing is within the scope of thepresent invention.

FIG. 5 displays a message flow diagram in which a BS updatessynchronization information using Release Order messaging. The trafficchannel is already established and the mobile station has moved from afirst cell to a second cell.

At 503 a traffic channel is established and synchronization informationis communicated. An MS 500 and a BS 502 communicate synchronizationinformation over traffic as shown by 504. The BS may then communicate aRelease Order to the MS. The Release Order includes Sync_IDs as shown at506. It should be appreciated that either the MS or the BS may initiatethe Release Order. In one embodiment, if the MS initiates the ReleaseOrder, the BS may respond with Release Order including thesynchronization information as shown at 506. In another embodiment, thebase station initiates the Release Order including the synchronizationinformation as shown at 506. The MS may then communicate a Release Orderto the BS as shown at 508.

In another embodiment, upon release of a call, the BS 502 sends aRelease Order, Extended Release Message, or Extended ReleaseMini-Message to update the current synchronization information in the MS500. In accordance with the teachings of the present invention, inaddition to communicating configuration related information on the SCRand NNSCR of the call, the synchronization information may conveyadditional information, such as mobile IP information and/or GenericRouting Encapsulation (GRE) Key information for a GRE tunnel.

FIG. 6 displays a message flow diagram in which a BS updatessynchronization information with a Release Order on a Common Channel. Inone embodiment, the message flow diagram depicted in FIG. 6 occurs in anidle state. An MS 600 communicates an origination message includingsynchronization information (i.e., Sync_IDs) 604 to a BS 602. The BS 602then communicates a Release Order including synchronization information606 to the MS 600. In another embodiment, the BS 602 may also use theRelease Order while in a Mobile Station Idle State to update thesynchronization information stored in the MS 600. This is especiallyuseful when the MS 600 updates its packet data zone information while inIdle.

FIG. 7A displays a message flow diagram in which the MS performs aquery. An MS 700 generates a Status Request Message includingsynchronization information 704 and communicates the Status RequestMessaging including synchronization information 704 to the BS 702. TheBS 702 then generates a Status Response Message includingsynchronization information 706 to the MS 700.

Since the BS 702 can store multiple instances of synchronizationinformation, there is a chance that the synchronization informationstored in the MS 700 and BS 702 may not be synchronized. In accordancewith the teachings of the present invention, we propose to allow a MS700 to query (i.e., in CDMA, use Status Request Message, or othermessages that have the query capability) the synchronization informationstored in the BS 702 either in BS 702 Idle State or in traffic mode(i.e., mobile station can use Status Response Message or other messagesthat have the ability to report the stored Sync_ID).

FIG. 7B displays a message flow diagram in which the BS performs aquery. A BS 702 generates a Status Request Message includingsynchronization information 708 and communicates the Status RequestMessaging including synchronization information 708 to the MS 700. TheMS 700 then generates a Status Response Message includingsynchronization information 710 to the BS 702.

Since the MS 700 can store multiple instances of synchronizationinformation, there is a chance that the synchronization informationstored in the MS 700 and BS 702 may not be synchronized. In accordancewith the teachings of the present invention, we propose to allow an BS700 to query (i.e., in CDMA, use Status Request Message, or othermessages that have the query capability) the synchronization informationstored in the MS 702 either in MS 702 Idle State or in traffic mode(i.e., mobile station can use Status Response Message or other messagesthat have the ability to report the stored Sync_ID).

The synchronization information is used to communicate additionalinformation between the MS 700 and the BS 702, such as informationidentifying services or components in the wireless network. In addition,the synchronization information is communicated between the MS 700 andthe BS 702 using a variety of different mechanisms. For example, thesynchronization information is communicated using Release Order Messagesor Handoff Messages.

The following text identifies specific sections of the TIA/EIAIS-2000.5-C, Signaling Standards for cdma2000 Spread SpectrumSystems—Release C, May 2002, which is herein incorporated by referencethat may be updated to implement the teachings of the present invention.It should also be appreciated that implementing the teachings of thepresent invention using the Extended Release Message or Extended ReleaseMini-Message as defined in TIA/EIA IS-2000.5-C, Signaling Standards forcdma2000 Spread Spectrum Systems—Release C, May 2002 are similar to themethods disclosed when using the Release Order Message. It should beappreciated that the following text discloses the teachings of thepresent invention using a single Sync_ID in the Release Order. Inanother embodiment, multiple Sync_IDs may be included in the ReleaseOrder by including an extra field to indicate the number of Sync_IDsincluded in the message, by sub-dividing the current Sync_ID field, etc.

2.6.3.3 Page Response Substate

In this substate, the mobile station sends a Page Response Message or aReconnect Message in response to a mobile-station-addressed page from abase station. If the mobile station sends a Reconnect Message, it shallset the ORIG_IND field of the message to ‘0’.

[ . . . ]

-   -   14. Release Order: If NDSS_ORIG_(s) is equal to enabled, the        mobile station shall set NDSS_ORIG_(s) to disabled, and should        indicate to the user that the call origination has been        canceled. The mobile station shall enter the Mobile Station Idle        State or the System Determination Substate of the Mobile Station        Initialization State with a release indication (see 2.6.1.1). If        the mobile station enters the Mobile Station Idle State, and if        PACA_(s) is equal to enabled, the mobile station shall set        PACA_(s) to disabled and PACA_CANCEL to ‘0’, shall disable the        PACA state timer, and should indicate to the user that the PACA        call has been canceled. If P_REV_IN_USE_(s) is equal to or        greater than eleven, ORDQ is equal to ‘00000000’, and        SYNC_ID_INCL_(r) is equal to ‘1’, the mobile station shall        update the synchronization identifier received from the base        station corresponding to the current service configuration        (SYNC_ID_(s)=SYNC_ID_(r)).        [ . . . ]

2.6.3.5 Mobile Station Origination Attempt Substate

In this substate, the mobile station sends an Origination Message or aReconnect Message. If the mobile station sends a Reconnect Message, itshall set the ORIG_IND field of the message to ‘1’.

The mobile station shall not send the Reconnect Message ifRECONNECT_MSG_IND_(s) equals ‘0’ or if this message is not being sent toreconnect a dormant packet data service instance.

[ . . . ]

-   -   16. Release Order: If NDSS_ORIG_(s) is equal to enabled, the        mobile station shall set NDSS_ORIG_(s) to disabled, and should        indicate to the user that the call origination has been        canceled. The mobile station shall enter the Mobile Station Idle        State or the System Determination Substate of the Mobile Station        Initialization State with a release indication (see 2.6.1.1). If        the mobile station enters the Mobile Station Idle State, and if        PACA_(s) is equal to enabled, the mobile station shall set        PACA_(s) to disabled and PACA_CANCEL to ‘0’, shall disable the        PACA state timer, and should indicate to the user that the PACA        call has been canceled. If P_REV_IN_USE_(s) is equal to or        greater than eleven, ORDQ is equal to ‘00000000’, and        SYNC_ID_INCL_(r) is equal to ‘1’, the mobile station shall        update the synchronization identifier received from the base        station corresponding to the current service configuration        (SYNC_ID_(s)=SYNC_ID_(r)).

2.6.3.6 Registration Access Substate

In this substate, the mobile station sends a Registration Message. Ifthe base station responds with an authentication request, the mobilestation responds in this substate.

[ . . .]

-   -   13. Release Order: If NDSS_ORIG_(s) is equal to enabled, the        mobile station shall set NDSS_ORIG_(s) to disabled, and should        indicate to the user that the call origination has been        canceled. The mobile station shall enter the Mobile Station Idle        State or the System Determination Substate of the Mobile Station        Initialization State with a release indication (see 2.6.1.1). If        the mobile station enters the Mobile Station Idle State, and if        PACA_(s) is equal to enabled, the mobile station shall set        PACA_(s) to disabled and PACA_CANCEL to ‘0’, shall disable the        PACA state timer, and should indicate to the user that the PACA        call has been canceled. If P_REV_IN_USE_(s) is equal to or        greater than eleven, ORDQ is equal to ‘00000000’, and        SYNC_ID_INCL_(r) is equal to ‘1’, the mobile station shall        update the synchronization identifier received from the base        station corresponding to the current service configuration        (SYNC_ID_(s)=SYNC_ID_(r)).        [ . . . ]

2.6.4.3 Traffic Channel Substate

In this substate, the mobile station may exchange Traffic Channel frameswith the base station in accordance with the current serviceconfiguration. The mobile station may perform the gating operation ofReverse Pilot Channel.

[ . . . ]

If the mobile station receives a message which is included in thefollowing list and every message field value is within its permissiblerange, the mobile station shall process the message as described belowand in accordance with the message's action time (see 2.6.4.1.5).

[ . . . ]

-   -   42. Release Order: The Layer 3 shall send a “release indication”        to all Call Control instances, the mobile station shall perform        the following:        -   If P_REV_IN_USE_(s) is equal to or greater than eleven, ORDQ            is equal to ‘00000000’, and SYNC_ID_INCL_(r) is equal to            ‘1’, the mobile station shall update the synchronization            identifier received from the base station corresponding to            the current service configuration (SYNC_ID_(s)=SYNC_ID_(r)).        -   The mobile station shall enter the Release Substate with a            base station release indication (see 2.6.4.4).            [ . . . ]

2.6.4.4 Release Substate

In this substate, the mobile station confirms the disconnect of allcalls and physical channels.

Upon entering the Release Substate, the mobile station shall perform thefollowing:

[ . . . ]

-   -   If the mobile station enters the Release Substate with a service        inactive indication, the mobile station shall send a Release        Order (ORDQ=‘00000010’), and set RETURN_CAUSE_(s) to ‘0000’.    -   If the mobile station enters the Release Substate with a base        station release indication, the mobile station shall send a        Release Order (ORDQ=‘00000000’). The Layer 3 shall terminate all        Call Control instances. The mobile station shall disable its        transmitter, set RETURN_CAUSE_(s) to ‘0000’, and shall perform        the procedures as specified in 2.6.4.4.1.        [ . . . ]    -   If the mobile station receives a message which is included in        the following list, and if every message field value is within        its permissible range, the mobile station shall process the        message as described below and in accordance with the message's        action time (see 2.6.4.1.5):    -   [ . . . ]    -   24. Release Order: The mobile station shall disable its        transmitter. The Layer 3 shall terminate all Call Control        instances. The mobile station shall perform the following:        -   If P_REV_IN_USE_(s) is equal to or greater than eleven, ORDQ            is equal to ‘00000000’, and SYNC_ID_INCL_(r) is equal to            ‘1’, the mobile station shall update the synchronization            identifier received from the base station corresponding to            the current service configuration (SYNC_ID_(s)=SYNC_ID_(r)).        -   If the mobile station enters the Release Substate with a            power-down indication, the mobile station may power down;            otherwise, the mobile station shall perform the procedures            as specified in 2.6.4.4.1            [ . . . ]

2.6.4.4.1 Procedures for Exiting the Release Substate

The mobile station shall perform the following procedures to determinewhether to enter the Mobile Station Idle State or System DeterminationSubstate of the Mobile Station Initialization State.

[ . . . ]

2.7.4 Information Records

On the r-csch, information records may be included in the StatusResponse Message, the Extended Status Response Message, the OriginationMessage, and the Device Information Message. On the r-dsch, informationrecords may be included in the Origination Continuation Message, theEnhanced Origination Message, the Flash With Information Message, theExtended Flash With Information Message, the Service Request Message,the Service Response Message, the Status Message, and the StatusResponse Message. Table 2.7.4-1 lists the information record type valuesthat may be used with each message type. The following sections describethe contents of each of the record types in detail.

[ . . . ]

TABLE 2.7.4-1 Information Record Types (Part 3 of 3) Record Type Messager- r- Information Record (binary) Type csch dsch P_REV_IN_USE SignalingMessage Integrity 00100100 Status [2] Y Y ≧10 Capability STORED_SYNC_ID00100101 Status [2] Y Y ≧11 Extended Record Type - 11111110Country-Specific 1, ≧4 International All other record type values arereserved. “Flash” refers to either the Flash With Information Message orthe Extended Flash With Information Message. “DIM” refers to the DeviceInformation Message. [1] This information record may be included in aStatus Message, a Status Response Message, or an Extended StatusResponse Message. [2] This information record may be included in aStatus Response Message or an Extended Status Response Message.[ . . . ]

2.7.4.36 Stored SYNC_ID

This information record can be included in a Status Response Message oran Extended Status Response Message to return the mobile station storedSYNC_ID.

Type-Specific Field Length (bits) NUM_SYNC_ID 3

-   -   NUM_SYNC_ID occurrences of the following two-field record:

SYNC_ID_LEN 0 or 4 SYNC_ID 0 or (8 × SYNC_ID_LEN)

-   NUM_SYNC_ID—Number of Service Configuration synchronization    identifier.    -   The mobile station shall set this field to the number of Service        Configuration synchronization identifier stored by the mobile        station. The mobile station shall set this field to ‘000’ if no        SYNC_ID is stored.-   SYNC_ID_LEN—Service Configuration synchronization identifier length.    -   If the SYNC_ID_INCL field is set to ‘000’, the base station        shall omit this field; otherwise, the base station shall include        this field and set it as follows:    -   The base station shall set this field to the length (in octets)        of the SYNC_ID field included in this message. The base station        shall set this field to a value larger than zero.-   SYNC_ID—Service Configuration synchronization identifier.    -   If the SYNC_ID_INCL field is set to ‘000’, the base station        shall omit this field; otherwise, the base station shall include        this field and set it as follows:    -   The base station shall set this field to the synchronization        identifier corresponding to the service configuration conveyed        by this message.

3.7.2.3.2.15 Status Request Message

MSG_TAG: STRQM

Field Length (bits) RESERVED 4 QUAL_INFO_TYPE 8 QUAL_INFO_LEN 3Type-specific fields 8 □ QUAL_INFO_LEN NUM_FIELDS 4

-   -   NUM_FIELDS occurrences of the following field:

RECORD_TYPE 8[ . . . ]

TABLE 3.7.2.3.2.15-2 Status Information Record Types Record Type (seeTable 2.7.4- Information Record 1) QUAL_INFO_TYPE Requested (binary)(binary) Reserved for obsolete 00000110 — Identification Call Mode00000111 00000000 Terminal Information 00001000 00000010 RoamingInformation 00001001 00000010 Security Status 00001010 00000000 IMSI00001100 00000000 ESN 00001101 00000000 Band Class Information 0000111000000000 Power Class Information 00001111 00000010 Operating ModeInformation 00010000 00000001 Service Option Information 0001000100000010 Multiplex Option Information 00010010 00000010 ServiceConfiguration 00010011 00000000 Power Control Information 0001011100000000 IMSI_M 00011000 00000000 IMSI_T 00011001 00000000 CapabilityInformation 00011010 00000000 Channel Configuration 00011011 00000000Capability Information Extended Multiplex Option 00011100 00000000Information Geo-location Information 00011110 00000000 Band SubclassInformation 00011111 00000001 Hook Status 00100001 00000000 EncryptionCapability 00100011 00000000 STORED_SYNC_ID 00100101 00000000 All otherrecord type values are reserved.

TABLE 3.7.4-1 Order and Order Qualification Codes Used on the f-csch andthe f-dsch (Part 2 of 4) Order Qual- Order ification Additional Code,Code, ACTION_TIME Fields f-csch f-dsch ORDER ORDQ can be other thanOrder Order (binary) (binary) specified ORDQ P_REV_IN_USE Name/FunctionN Y 010011 00000000 Y Y  <7 Service Option Request Order (Band Class 0only) (see 3.7.4.2) N Y 010100 00000000 Y Y  <7 Service Option ResponseOrder (Band Class 0 only; see 3.7.4.3) Y Y 010101 00000000 N Y AllRelease Order (no reason given. See 3.7.4.10 for additional fields otherthan ORDQ if the P_REV_IN_USE ≧ 11.) Y Y 010101 00000010 N N All ReleaseOrder (indicates that requested service option is rejected) N Y 01010100000011 N Y ≧9 Release Order (Enhanced Release Order to direct themobile station to Mobile Station Idle State or System DeterminationSubstate; see 3.7.4.8) N Y 010110 00000000 N N All Outer Loop ReportRequest Order

3.7.4.10 Release Order

If P_REV_IN_USE≧11, the Release Order with ORDQ=‘00000000’ andadditional field other than ORDQ can be sent on the either f-csch orf-dsch to update station's SYNC_ID if included.

Order-Specific Field Length (bits) ORDQ 8

-   -   If the ORDQ is ‘00000000’, the mobile station shall include the        following order-specific record:

SYNC_ID_INCL 1 SYNC_ID_LEN 0 or 4 SYNC_ID 0 or (8 × SYNC_ID_LEN)

-   ORDQ—Order qualification code.    -   The base station shall set this field to ‘00000000’.-   SYNC_ID_INCL—Service Configuration synchronization identifier    included indicator.    -   The base station shall set this field to ‘1’ if the SYNC_ID        field is included in this message; otherwise, the base station        shall set this field to ‘0’.-   SYNC_ID_LEN—Service Configuration synchronization identifier length.    -   If the SYNC_ID_INCL field is set to ‘0’, the base station shall        omit this field; otherwise, the base station shall include this        field and set it as follows:    -   The base station shall set this field to the length (in octets)        of the SYNC_ID field included in this message. The base station        shall set this field to a value larger than zero.-   SYNC_ID—Service Configuration synchronization identifier.    -   If the SYNC_ID_INCL field is set to ‘0’, the base station shall        omit this field; otherwise, the base station shall include this        field and set it as follows:    -   The base station shall set this field to the synchronization        identifier corresponding to the service configuration conveyed        by this message.

In another embodiment to the present invention, Handoff Messages may beused to communicate the synchronization information between the MS andthe BS. The following Handoff Direction Messages are used to update theSync_ID information in the corresponding sections of the TIA/EIAIS-2000.5-C, Signaling Standards for cdma2000 Spread SpectrumSystems—Release C, May 2002 to communicate Sync_ID information thatidentifies services or components in a wireless network.

2.6.6.2.5 Handoff Messages

2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages

If the mobile station receives any of the following messages, then themobile station shall process the message as described.

[ . . . ]

-   -   11. Universal Handoff Direction Message: The mobile station        shall process the message as follows:        -   In addition to the requirements in this section, if the            SCR_INCLUDED field is included in this message and is set to            ‘1’ the mobile station shall also process this message in            accordance with the requirements for the active service            subfunction (see 2.6.4.1.2.2).            [ . . . ]    -   If NNSCR_INCLUDED field is included and set to ‘1’ and        SCR_INCLUDED field is either not included or included but set to        ‘0’, the mobile station shall process the received        Non-negotiable Service Configuration Record as specified in        2.6.4.1.13 at the action time of this message. If the        synchronization identifier is received from the base station        corresponding to this updated service configuration:    -   The mobile station shall store (if included) the synchronization        identifier received from the base station corresponding to this        service configuration (SYNC_IDs=SYNC_ID_(r)).    -   The mobile station shall store the current service configuration        as specified in 2.6.4.1.2.2.5.1 at the action time of this        message.    -   Otherwise, the mobile station shall set SYNC_ID_(s) to NULL.    -   If SYNC_ID_INCL_(r) is set to ‘1’, NNSCR_INCLUDED field is not        included or is included and set to ‘0’, and SCR_INCLUDED is not        included or is included and set to ‘0’, the mobile station shall        perform the following:    -   The mobile station shall store the synchronization identifier        received from the base station (SYNC_ID_(s)=SYNC_ID_(r)).    -   If the currently used service configuration has a corresponding        SYNC_ID, SID_INCL_(r) is set to ‘0’ and NID_INCL_(r) is set to        ‘0’, the mobile station shall update the stored SYNC_ID value        corresponding to the currently used service configuration with        SYNC_ID_(r).    -   If the currently used service configuration has a corresponding        SYNC_ID, SID_INCL_(r) is set to ‘1’, or NID_INCL_(r) is set to        ‘1’, the mobile station shall perform one of the following:        -   If either SID_(r) or NID_(r) included in the message is not            equal to the stored SID or NID corresponding to the            currently used service configuration, the mobile station            shall store the current service configuration as specified            in 2.6.4.1.2.2.5.1 at the action time of this message.        -   Otherwise, the mobile station shall update the stored            SYNC_ID value corresponding to the currently used service            configuration with SYNC_ID_(r).    -   If the currently used service configuration does not have a        corresponding SYNC_ID, the mobile station shall store the        current service configuration as specified in 2.6.4.1.2.2.5.1 at        the action time of this message.

When the message takes effect, the mobile station shall perform thefollowing actions:

[ . . . ]

-   -   Store the following parameters from the Universal Handoff        Direction Message:        -   Universal Handoff Direction Message sequence number            (HDM_SEQ_(s)=HDM_SEQ_(r))        -   Forward power control subchannel relative gain            (FPC_SUBCHAN_GAIN_(s)=FPC_SUBCHAN_GAIN_(r)).        -   If the mobile station uses FPC_SUBCHAN_GAIN_(s), the mobile            station shall perform the following:        -   [ . . . ]        -   If SID_INCL_(r) is equal to ‘1’, the mobile station shall            store the following:            -   System identification (SID_(s)=SID_(r))        -   If NID_INCL_(r) is equal to ‘1’, the mobile station shall            store the following:            -   Network identification (NID_(s)=NID_(r))        -   If CH_IND_(r) is equal to ‘101’, the mobile station shall            perform the following:            [ . . . ]

3.7.3.3.2.36 Universal Handoff Direction Message

MSG_TAG: UHDM

Field Length (bits) USE_TIME 1 ACTION_TIME 0 or 6 [ . . . ] [ . . . ]SYNC_ID_INCL 0 or 1 SYNC_ID_LEN 0 or 4 SYNC_ID 0 or (8 × SYNC_ID_LEN) [. . . ] [ . . . ][ . . . ]

SYNC_ID_INCL—Service Configuration synchronization identifier includedindicator.

-   -   If the SCR_INCLUDED field is included and is set to ‘1’ or the        NNSCR_INCLUDED field is included and is set to ‘1’, or        P_REV_IN_USE is equal or greater than 11, the base station shall        include this field; otherwise, the base station shall omit this        field. If included, the base station shall set this field as        follows:    -   The base station shall set this field to ‘1’ if the SYNC_ID        field is included in this message; otherwise, the base station        shall set this field to ‘0’.

SYNC_ID_LEN—Service Configuration synchronization identifier length.

-   -   If the SYNC_ID_INCL field is not included or is included and is        set to ‘0’, the base station shall omit this field; otherwise,        the base station shall include this field and set it as follows:    -   The base station shall set this field to the length (in octets)        of the SYNC_ID field included in this message. The base station        shall set this field to a value larger than zero.

SYNC_ID—Service Configuration synchronization identifier.

-   -   If the SYNC_ID_INCL field is not included or is included and is        set to ‘0’, the base station shall omit this field; otherwise,        the base station shall include this field and set it as follows:    -   If the SCR_INCLUDED field is included and is set to ‘1’ or the        NNSCR_INCLUDED field is included and is set to ‘1’, the base        station shall set this field to the synchronization identifier        corresponding to the service configuration conveyed by this        message; otherwise, the base station shall set this field to the        updated synchronization identifier corresponding to the current        service configuration.

While the present invention is described herein with reference toillustrative embodiments for particular applications, it should beunderstood that the invention is not limited thereto. Those havingordinary skill in the art and access to the teachings provided hereinwill recognize additional modifications, applications, and embodimentswithin the scope thereof and additional fields in which the presentinvention would be of significant utility.

It is, therefore, intended by the appended claims to cover any and allsuch applications, modifications, and embodiments within the scope ofthe present invention.

1. A method of operating comprising: a first communication devicereceiving synchronization information from a second communication deviceusing network messaging in a wireless communication network, thesynchronization information capable of use for synchronization; and thecommunication device implementing a network function other thansynchronization by interpreting the synchronization information.
 2. Themethod of claim 1, wherein the synchronization information is a Sync_ID.3. The method of claim 2, wherein the synchronization informationfurther comprises multiple Sync_IDs.
 4. The method of claim 1, whereinthe network function includes identifying a network component.
 5. Themethod of claim 1, wherein the network function includes a networkservice.
 6. The method of claim 1, wherein the network messaging is aRelease Order Message.
 7. The method of claim 1, wherein the networkmessaging is an Extended Release Message.
 8. The method of claim 1,wherein the network messaging is a Extended Release Mini Message.
 9. Themethod of claim 1, wherein interpreting the synchronization informationcomprises using the synchronization information as an index to search adatabase to access a value that may be used to implement the networkfunction other than synchronization. 10-20. (canceled)
 21. The method ofclaim 1, wherein the first communication device comprises a base stationand wherein the second communication device comprises a mobile station.22. A first device, comprising: wireless communication circuitry forperforming wireless communication with a second device; and processinghardware coupled to the wireless communication circuitry, wherein theprocessing hardware is configured to: receive synchronizationinformation from the second communication device using network messagingin a wireless communication network, the synchronization informationcapable of use for synchronization; and implement a network functionother than synchronization by interpreting the synchronizationinformation.
 23. The first device of claim 22, wherein thesynchronization information is a Sync_ID.
 24. The first device of claim22, wherein the network function includes identifying a networkcomponent.
 25. The first device of claim 22, wherein the networkfunction includes a network service.
 26. The first device of claim 22,wherein the network messaging comprises one or more of: a Release OrderMessage; an Extended Release Message; or an Extended Release MiniMessage.
 27. A non-transitory, computer accessible memory medium storingprogram instructions executable by a first device to: receivesynchronization information from a second communication device usingnetwork messaging in a wireless communication network, thesynchronization information capable of use for synchronization; andimplement a network function other than synchronization by interpretingthe synchronization information.
 28. The non-transitory, computeraccessible memory medium of claim 27, wherein the synchronizationinformation is a Sync_ID.
 29. The non-transitory, computer accessiblememory medium of claim 27, wherein the network function includesidentifying a network component.
 30. The non-transitory, computeraccessible memory medium of claim 27, wherein the network functionincludes a network service.
 31. The non-transitory, computer accessiblememory medium of claim 27, wherein the network messaging comprises oneor more of: a Release Order Message; an Extended Release Message; or anExtended Release Mini Message.
 32. A method comprising: a firstcommunication establishing wireless communication with a secondcommunication device; the first communication device determining anetwork function for implementation by the second communication devicethe first communication device transmitting synchronization informationto the second communication device using network messaging in a wirelesscommunication network, wherein the synchronization information iscapable for use in synchronization and for implementing the networkfunction, wherein the network function is not a synchronization functionand is implementable by interpreting the synchronization information.33. The method of claim 32, wherein the synchronization informationcomprises a Sync_ID.
 34. The method of claim 32, wherein the networkfunction includes identifying a network component.
 35. The method ofclaim 32, wherein the network function includes a network service. 36.The method of claim 32, wherein the network messaging is a Release OrderMessage.
 37. The method of claim 32, wherein the network messaging is anExtended Release Message.
 38. The method of claim 32, wherein thenetwork messaging is a Extended Release Mini Message.
 39. The method ofclaim 32, wherein the synchronization information is usable as an indexto search a database to access a value that may be used to implement thenetwork function other than synchronization.
 40. The method of claim 32,wherein the first communication device comprises a mobile station andwherein the second communication device comprises a base station.
 41. Afirst device, comprising: wireless communication circuitry forperforming wireless communication with a second device; and processinghardware coupled to the wireless communication circuitry, wherein theprocessing hardware is configured to: establish wireless communicationwith the second device using the wireless communication circuitry;determine a network function for implementation by the secondcommunication device transmit synchronization information to the secondcommunication device using network messaging in a wireless communicationnetwork via the wireless communication circuitry, wherein thesynchronization information is capable for use in synchronization andfor implementing the network function, wherein the network function isnot a synchronization function and is implementable by interpreting thesynchronization information.
 42. The first device of claim 41, whereinthe synchronization information is a Sync_ID.
 43. The first device ofclaim 41, wherein the network function includes identifying a networkcomponent.
 44. The first device of claim 41, wherein the networkfunction includes a network service.
 45. The first device of claim 41,wherein the network messaging comprises one or more of: a Release OrderMessage; an Extended Release Message; or an Extended Release MiniMessage.
 46. A non-transitory, computer accessible memory medium storingprogram instructions executable by a first device to: establish wirelesscommunication with a second communication device; determine a networkfunction for implementation by the second communication device transmitsynchronization information to the second communication device usingnetwork messaging in a wireless communication network, wherein thesynchronization information is capable for use in synchronization andfor implementing the network function, wherein the network function isnot a synchronization function and is implementable by interpreting thesynchronization information.
 47. The non-transitory, computer accessiblememory medium of claim 46, wherein the synchronization information is aSync_ID.
 48. The non-transitory, computer accessible memory medium ofclaim 46, wherein the network function includes identifying a networkcomponent.
 49. The non-transitory, computer accessible memory medium ofclaim 46, wherein the network function includes a network service. 50.The non-transitory, computer accessible memory medium of claim 46,wherein the network messaging comprises one or more of: a Release OrderMessage; an Extended Release Message; or an Extended Release MiniMessage.